Mention bind_textdomain_codeset in faq

svn path=/trunk/; revision=20795

diff --git a/docs/reference/ChangeLog b/docs/reference/ChangeLog
index 5866135f15bf54da5ca1de06b677aaa892f5038a..d114924b1d227fda25a1e417fa9865b9b139bb35 100644 (file)
--- a/docs/reference/ChangeLog
+++ b/docs/reference/ChangeLog
@@ -1,3 +1,9 @@
+2008-07-06  Matthias Clasen  <mclasen@redhat.com>
+
+       Bug 488019 - Mention bind_textdomain_codeset in gettext related FAQ
+
+       * gtk/question_index.sgml: Mention bind_textdomain_codeset()
+
 2008-07-05  Matthias Clasen  <mclasen@redhat.com>
 
        * === Released 2.13.4 ===

diff --git a/docs/reference/gtk/question_index.sgml b/docs/reference/gtk/question_index.sgml
index 40923f174a1526ca207a1a3326854db924e270a0..c8d638de67c11e4b2b95eda6d8f16b2845675c61 100644 (file)
--- a/docs/reference/gtk/question_index.sgml
+++ b/docs/reference/gtk/question_index.sgml
@@ -190,9 +190,10 @@ to read the documentation.
 <para>
 The short checklist on how to use gettext is: call bindtextdomain() so gettext 
 can find the files containing your translations, call textdomain() to set the 
-default translation domain, then call gettext() to look up each string to be 
-translated in the default domain. Conventionally, people define macros as
-follows for convenience:
+default translation domain, call bind_textdomain_codeset() to request that
+all translated strings are returned in UTF-8, then call gettext() to look up 
+each string to be translated in the default domain. 
+Conventionally, people define macros as follows for convenience:
 <informalexample>
 <programlisting>
   #define  _(x)  gettext (x)
@@ -354,6 +355,11 @@ g_print(text);
 g_free (text);
 </programlisting></informalexample>
 </para>
+<para>
+If you are using gettext() to localize your application, you need to
+call bind_textdomain_codeset() to ensure that translated strings are
+returned in UTF-8 encoding.
+</para>
 </answer>
 </qandaentry>